Operational Domain Systems Engineering

Recently in the INCOSE Insight, Fellow’s Edition, Jeffrey O. Grady [1] discussed Robert E. Machol’s 1965 concept of the “T-Shaped” domain knowledge of the systems engineer. He challenged that in reality, most systems engineers are somewhat broader in knowledge than just their core discipline. In effect, there is a movement to become “domain” systems engineers with general knowledge of the various technical specialties that contribute to that field. While much has been written on requirements analysis, subtle variations in describing a problem can still have major impacts on the potential solutions being sought or the usefulness of the solution selected. Underestimating the value of operational domain knowledge, or not being able to effectively convey the knowledge can lead a project towards a poor or suboptimal solution. This gives rise to the concept of operational domain systems engineering knowledge.